inline cache造句

• V8 elision of expensive runtime properties, and inline caching, among many others.
• Real Smalltalk implementations often use a technique known as inline caching that makes method dispatch very fast.
• A naive implementation of monomorphic inline caching would therefore constantly cycle through the " uninitialized " and " monomorphic " states.
• Inline caching basically stores the previous destination method address and object class of the call site ( or multiple pairs for multi-way caching ).
• In order to prevent this from happening, most implementations of monomorphic inline caching support a third state often referred to as the " megamorphic " state.
• To achieve better performance, many language runtimes employ some form of non-inline caching where the results of a limited number of method lookups are stored in an associative data structure.
• However, the quality of code it generates might not be as good as the one that is JITed, for the same reasons why code compiled statically, without profile-guided optimization, cannot be as good as JIT compiled code in the extreme case : the lack of profiling data to drive, for instance, inline caching.
• Once a call site has entered the " megamorphic " state, it will behave just as it did in the " uninitialized " state with the exception that it will not enter the " monomorphic " state ever again ( some implementations of monomorphic inline caching will change " megamorphic " call sites back to being " uninitialized " after a certain amount of time has passed or once a full garbage collection cycle is performed ).